Hi, is there any chance to merge this one? I would really appreciate it, thanks a lot 🤞

@yuniorsk please could you explain why it's necessary to put those methods into a trait?
Sure, the classfile "Event" itself gets smaller and but not the loaded class as it uses that trait.

Additionally you need to check both classes, Event and ManagesFrequencies to get a picture of the class Event.

Furthermore for me it does not seem to be "good practice" to let the trait access the Event property $this->_expression which is part of the Event and not of the trait. Not a "good practice", cause you rely on the fact that all classes using the trait needs a property "_expression" in order to work (instead of defining an abstract method within the trait "abstract protected function getExpression()“ to require a kind of an interface for the trait).

Please do not get me wrong. I am a bit skeptical when it comes to traits as they easily can mess up things in big projects.

@darealfive I am only interested in missing methods like hourlyAt etc. I don't mind if it's extracted into trait or not.

I have already cheered for these missing api methods here #41, but with no luck 🤷‍♂️ If there some way I can help with it just let me know